Summary
This PR adds documentation and configuration examples for how the Prometheus Operator discovers monitoring targets using ServiceMonitors and Probes in a Kubernetes environment.

Prometheus Operator ServiceMonitor Discovery
The Prometheus Operator manages Prometheus instances using a Kubernetes Custom Resource (CR) called Prometheus.
ServiceMonitors are custom resources that define how Prometheus should discover and scrape metrics endpoints from Kubernetes Services.
The Operator automatically watches for ServiceMonitors in specified namespaces (or all namespaces, if configured).

Discovery process:
The Operator reads the serviceMonitorSelector and serviceMonitorNamespaceSelector fields in the Prometheus CR.
It finds all ServiceMonitors matching the selectors.
For each ServiceMonitor, it matches the selector.matchLabels to Services in the target namespace(s).
For each matching Service, it scrapes the specified port and path (e.g., /metrics or /actuator/prometheus).

Benefits:
Dynamic, label-based discovery of services to monitor.
No need to manually edit Prometheus config for new services.
Supports multi-namespace and multi-team setups.

Prometheus Operator Probe Discovery
Probes are custom resources (if enabled) that define blackbox monitoring checks (e.g., HTTP, TCP, ICMP) using the blackbox exporter.
The Operator watches for Probe resources using probeSelector and probeNamespaceSelector in the Prometheus CR.

Discovery process:
The Operator finds all Probe resources matching the selectors.
For each Probe, it configures Prometheus to scrape the blackbox exporter with the specified module and target(s).
Probes are ideal for monitoring external endpoints, APIs, or HTTP health of services (including databases or exporters).

Benefits:
Enables synthetic monitoring (probes) alongside service scraping.
Centralizes all monitoring configuration in Kubernetes resources.
Key Features Enabled by This PR
Automatic discovery of all ServiceMonitors and Probes in the cluster (with {} selectors).
No need for static scrape configs—all targets are managed via Kubernetes resources.
Supports both application metrics (via ServiceMonitors) and endpoint health checks (via Probes).
RBAC configuration ensures Prometheus can discover targets across namespaces.